Sharing timed fingerprint location information

ABSTRACT

Sharing timed fingerprint location information is disclosed. In an aspect, timed fingerprint location information can be associated with a location of a user equipment. This timed fingerprint location information can be shared with other devices. As such, with proper analysis, these other devices can employ the shared timed fingerprint location information to determine their location. In an aspect, the other devices can determine that they are located at the same location as the user equipment. However, a level of error can be inherent in the location determined from shared timed fingerprint location information. In some embodiments, this error can be compensated for.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of, and claims priority to, U.S.patent application Ser. No. 13/284,497, filed 28 Oct. 2011, and entitled“SHARING TIMED FINGERPRINT LOCATION INFORMATION,” which application ishereby incorporated by reference in its entirety.

TECHNICAL FIELD

The disclosed subject matter relates to transportation analytics and,more particularly, to employing mobile devices as data sources fortransportation analytics.

BACKGROUND

Conventional sources of location information for mobile devices arebased on a wide variety of location determination technologies, such asglobal positioning system (GPS) technology, triangulation,multilateration, etc. These sources of data have provided theopportunity to capture location information for a device and share itwith another device, which can allow non-location enabled devices toparticipate, at some level, in location-centric services. In contrast toconventional systems that rely on technologies such as GPS,triangulation, multilateration, etc., the use of timed fingerprintlocation (TFL) technology can provide advantages over the conventionaltechnologies. For example, GPS is well known to be energy intensive andto suffer from signal confusion in areas with interference between thesatellite constellation and the GPS enabled device. Further, GPS issimply not available on many mobile devices, especially where thedevices are cost sensitive. Multilateration and triangulationtechnologies are computationally intensive, which can result inprocessing time issues and a corresponding level of energy consumption.

The above-described deficiencies of conventional mobile device locationdata sources for transportation analytics is merely intended to providean overview of some of problems of current technology, and are notintended to be exhaustive. Other problems with the state of the art, andcorresponding benefits of some of the various non-limiting embodimentsdescribed herein, may become further apparent upon review of thefollowing detailed description.

BRIEF DESCRIPTION OF DRAWINGS

FIG. 1 is an illustration of a system that facilitates sharing TFLinformation in accordance with aspects of the subject disclosure.

FIG. 2 is a depiction of a system that facilitates sharing TFLinformation in accordance with aspects of the subject disclosure.

FIG. 3 illustrates a system that facilitates sharing TFL information inaccordance with aspects of the subject disclosure.

FIG. 4 is a depiction of a system that facilitates receiving shared TFLinformation in accordance with aspects of the subject disclosure.

FIG. 5 illustrates an exemplary system including shared TFL informationin accordance with aspects of the subject disclosure.

FIG. 6 illustrates a method facilitating sharing TFL information inaccordance with aspects of the subject disclosure.

FIG. 7 illustrates a method for requesting sharing of TFL information inaccordance with aspects of the subject disclosure.

FIG. 8 illustrates a method facilitating receiving shared TFLinformation in accordance with aspects of the subject disclosure.

FIG. 9 is a block diagram of an exemplary embodiment of a mobile networkplatform to implement and exploit various features or aspects of thesubject disclosure.

FIG. 10 illustrates a block diagram of a computing system operable toexecute the disclosed systems and methods in accordance with anembodiment.

DETAILED DESCRIPTION

The presently disclosed subject matter illustrates sharing timedfingerprint location (TFL) information. Sharing can allow devices toemploy TFL information from a TFL source device. As an example, a laptopwithout a GPS receiver can receive shared TFL information from aTFL-enabled cell phone, i.e., the TFL-enabled cell phone can be the TFLsource device. Based on the shared TFL information, the laptop candetermine where it is located, with some accepted level of error. Thisdetermined location, based on TFL information from a TFL source device,can enable location-centric features for the laptop. Theselocation-centric features might not otherwise have been enabled. As asecond example, a GPS enabled tablet computer can be located in abuilding and therefore have poor reception of GPS signals therebylimiting the ability of the tablet computer to determine its location.Shared TFL information can facilitate the laptop determining itslocation.

TFL information can include location information or timing information.Further, such information can be accessed from active state or idlestate user equipment. As such, TFL information component can facilitateaccess to location information or timing information for a mobile deviceor user equipment (UE) in an active or idle state. TFL information canbe information from systems in a timed fingerprint location wirelessenvironment, such as a TFL component of a wireless telecommunicationscarrier. As a non-limiting example, UEs, including mobile devices notequipped with a GPS-type system, can be associated with TFL information,which can facilitate determining a location for a UE based on the timinginformation associated with the UE.

In an aspect, TFL information can include information to determine adifferential value for a NodeB site pair and a bin grid frame. Acentroid region (possible locations between any site pair) for anobserved time value associated with any NodeB site pair (NBSP) can becalculated and is related to the determined value (in units of chip)from any pair of NodeBs. When UE time data is accessed, a value look-upcan be initiated (e.g., a lookup for “DV(?,X)” as disclosed in moredetail in the application incorporated herein by reference). RelevantNBSPs can be prioritized as part of the look-up. Further, the relevantpairs can be employed as an index to lookup a first primary set. As anexample, time data for a UE can be accessed in relation to a locatingevent in a TFL wireless carrier environment. In this example, it can bedetermined that a NBSP, with a first reference frame, be used forprimary set lookup with the computed DV(?,X) value as the index. Thiscan for example return a set of bin grid frame locations forming ahyperbola between the NodeBs of the NBSP. A second lookup can then beperformed for an additional relevant NBSP, with a second referenceframe, using the same value DV(?,X), as an index into the data set.Continuing the example, the returned set for the look up with secondNBSP can return a second set of bin grid frames. Thus, the UE is likelylocated in both sets of bin grid frames. Therefore, where the UE islikely in both sets, it is probable that the location for the UE is atan intersection of the two sets. Additional NBSPs can be included tofurther narrow the possible locations of the UE by providing additionalintersections among relevant bin grid sets. As such, employing TFLinformation for location determination is demonstrably different fromconventional location determination techniques or systems such as GPS,eGPS, triangulation or multilateration in wireless carrier environments,near field techniques, or proximity sensors.

Moreover, whereas TFL can be operable in a wide array of current andlegacy devices without any substantial dependence on GPS technologies, agreater number of mobile devices can act as TFL source devices thanwould be expected for GPS-enabled devices at the current time. A greaternumber of data sources is generally considered desirable in facilitatingaccess to location information. Further, where TFL information can beemployed in a lookup of location data sets, TFL can be much lesscomputationally intense than triangulation or multilaterationtechnologies. Reduced computational load is generally desirable in UEdevices. TFL can piggyback on timing signals employed in wirelesstelecommunications, which systems are already deployed. A reduced needto rollout of additional hardware is generally considered desirable.Additionally, by piggybacking on existing timing signals and by reducingthe computational load, TFL can be associated with minimal additionalenergy expenditure in sharp contrast to GPS ortriangulation/multilateration technologies. Reduced energy expenditureis generally related to reduced battery drain in mobile devices and istypically a highly desirable trait.

Various embodiments relate to sharing TFL information between userequipment. In one example embodiment, a system comprises a locationcomponent that receives timed fingerprint location information. Theexemplary system further comprises an access component that determines alevel of access to the TFL information. This level of access can beassociated with a request for access to the TFL information. A TFLinformation interface component can facilitate access to the TFLinformation based on the determined level of access.

In another example embodiment, a system comprises an antenna componentadapted for short-range communications. The system further comprises aninformation interface to facilitate communications related to sharingTFL information. A request to share TFL information can result inreceiving shared TFL information. The received shared TFL informationcan be stored in a memory component of the exemplary system.

In a further embodiment, a method comprises receiving TFL informationfor a UE. The example method further comprises receiving a request toshare the TFL information. Access to the TFL information can be allowedin response to the request to share the TFL information.

In another example embodiment, a method comprises generating a requestto share TFL information. The request can result in a receiving aportion of the TFL information.

The subject disclosure is now described with reference to the drawings,wherein like reference numerals are used to refer to like elementsthroughout. In the following description, for purposes of explanation,numerous specific details are set forth in order to provide a thoroughunderstanding of the subject disclosure. It may be evident, however,that the subject disclosure may be practiced without these specificdetails. In other instances, well-known structures and devices are shownin block diagram form in order to facilitate describing the subjectdisclosure.

FIG. 1 is an illustration of a system 100, which facilitates sharing TFLinformation in accordance with aspects of the subject disclosure. System100 can include timed fingerprint location information component (TFLIC)110. TFLIC 110 can facilitate access to TFL information. TFL informationcan be location information derived from TFL timing information or TFLtiming information that can facilitate determining a location. TFLtiming information can be for one or more NBSPs. TFL information can bederived from timing associated with one or more NBSPs.

TFLIC 110 can be communicatively coupled with timed fingerprint locationaccess authorization component (TFL-AAC) 120, hereinafter TFL-AAC orAAC. AAC 120 can determine a level of TFL information access based on arequest for access to TFL information. A request for access to TFLinformation can be received by a TFL source device. The request foraccess to TFL information can be generated by a device seeking to accessTFL information from a TFL source device. As an example, a GPS-enabledcellphone can generate a request to access TFL information from aTFL-enabled cellphone. The TFL-enabled cell phone can receive therequest for access to TFL information. AAC 120, in this example, candetermine that access to the TFL information of the TFL-enabled cellphone can be accessed by the GPS-enabled cell phone.

In an aspect, different levels of TFL information access can beassociated with accessing different sets of TFL information, differentamounts of TFL information, different types of TFL information, etc. Asan example, a limited access to TFL information can be associated withaccessing only a single TFL timing measurement in contrast to anunlimited access to TFL information that can be associated withaccessing many TFL timing measurements. As a second example, a limitedaccess to TFL information can be associated with accessing TFL timingmeasurement in contrast to an unlimited access to TFL information thatcan be associated with accessing location information derived from TFLmeasurements. As a third example, a limited access to TFL informationcan be associated with accessing instant TFL timing measurements incontrast to an unlimited access to TFL information that can beassociated with accessing historical TFL timing measurements. It is tobe noted that any other form of limiting access to TFL information fallswithin the scope of the present disclosure even where not explicitlyrecited herein for brevity and clarity.

AAC 120 can be communicatively coupled with timed fingerprint locationinformation interface component (TFL-IIC) 130, hereinafter TFL-IIC orIIC. IIC 130 can facilitate interaction between a TFL source device andother devices. In an embodiment, IIC 130 can facilitate receiving arequest for access to TFL information. As an example, IIC 130 canreceive a request for TFL information at a TFL enabled cellphone from anautomobile navigation system. In another embodiment, IIC 130 can provideinformation about a TFL source device to other devices. As an example,IIC 130 can generate a beacon indicating that a TFL source device isaccepting requests for TFL information. This exemplary beacon can allowlistening devices to begin requesting TFL information from theassociated TFL source device by way of system 100.

In an aspect, once the request for TFL information has been processedand a level of access determined, the TFL information can be accordinglyaccessed. The accessed TFL information can be employed to determine alocation. This determined location will inherently have some level oferror. The error can be associated with the error present in the TFLinformation itself, error associated with computation of a location formTFL information, or error associated with presuming the determinedlocation is similar or the same as that derived from the accessed TFLinformation. As an example of the later error, determining a locationfor TFL information from a TFL source device can simply be presuming thelocation of the requesting device and the TFL source device are thesame. Continuing the example, where the requesting device and the TFLsource device are indeed collocated, such as where a user's laptoprequests TFL information from a TFL-enabled cellphone of the user, theerror associated with the determined location can be minimal. Incontrast, where the requesting device and the TFL source device are notcollocated or are only temporarily collocated, such as where a firstcell phone on a subway car requests TFL information from a TFL sourcedevice on the subway platform as the subway car is departing, can beassociated with much larger errors in accuracy of a location presumed tobe the same for both the requesting device and the TFL source device.

Numerous correction techniques can be applied to correct for inherenterror in the location determined from the accessed TFL information.These particular techniques are beyond the scope of the subjectdisclosure although the use of any such correction technique fallswithin the present disclosure. As an example, where a requesting deviceis moving away from a TFL source device, this change in relativeposition can be determined and employed to compute a level of error orcorrection factor. As a second example, where a requesting device andTFL source device employ a communication technology associated with acommunication range, such as using Bluetooth with a range of about 10meters, this communication technology characteristic can be employed indetermining a level of error or correction factor.

In an embodiment, user actions can be associated with interactionsrelative to accessing TFL information for a TFL source device. Theseuser actions can be predetermined settings, automated settings, or canrequire user intervention. As an example, a device can be set toautomatically seek sharing of TFL information. As a second example, adevice can be set to share TFL information with predetermined sets ofdevices, such as sharing TFL information among all devices belonging toa single user. As a third example, a device can require specific inputto shared TFL information, such as “bumping” a requesting device and TFLsource device by emulating a fist-bump action between the two device.

FIG. 2 is a depiction of a system 200, which can facilitate sharing TFLinformation in accordance with aspects of the subject disclosure. System200 can include TFLIC component 210. TFLIC 210 can facilitate access toTFL information. TFLIC 210 can be communicatively coupled to TFL-AAC220. AAC 220 can determine a level of TFL information access based on arequest for access to TFL information. AAC 220 can be communicativelycoupled to TFL-IIC. IIC 130 can facilitate interaction between a TFLsource device and other devices.

AAC 220 can include TFL information history component 222. TFLinformation history component 222 can facilitate access to historic TFLinformation. In certain circumstances, access to historic TFLinformation can be shared by way of system 200. Historic TFLinformation, accessed by way of TFL information history component 222,can include historic timing information, historic location information,etc. One example includes accessing the TFL information of a TFL sourcedevice for the last 60 minutes, which can be shared, in a limited orunlimited manner, to allow another device to employ the shared TFLinformation, such as to determine, with a level of inherent error, thelocation of the other device over the last 60 minutes.

AAC 220 can further include decision engine component 224 that canfacilitate forming determinations relating to a sharing rule.Determinations can include satisfying a sharing rule, not satisfying asharing rule, satisfying part of a sharing rule, applying a sharing ruleto a set of information, etc. A determination relating to a sharing rulecan be related to TFL information or a level of access to TFLinformation. As a first example, where a sharing rule is satisfied whena UE owner is the same as a TFL source device owner, decision enginecomponent 224 can determine that this rule is satisfied by comparingowner information of the TFL source device and the UE. As a furtherexample, decision engine component 224 can apply a weighting rule to TFLinformation and historical TFL information, such as where a ruleindicates that a weighting factor relating to accessing historical TFLinformation of 10 x is to be applied to historical TFL information overone hour old, e.g., making access to historical information lessaccessible. Numerous other examples of specific sharing rules are notexplicitly recited for brevity but are to be considered within the scopeof the present disclosure.

In an aspect, decision engine component 224 can include rule component226 to facilitate forming determinations related to a sharing rule. Rulecomponent 226 can facilitate employing one or more sharing rules. Theserules can include rules for determining values pertinent to sharing TFLinformation. As one example, determining a value for a user input, e.g.,determining “bumping”, can be associated with granting a higher level ofTFL information access authorization. In an embodiment, rule component226 can be a rule engine that allows the application of logicaldeterminations to be embodied in one or more algorithms related tosharing TFL information. As a non-limiting example, rule component 226can generate a rule that allows unlimited access to TFL informationamong an enumerated set of UEs based on International Mobile EquipmentIdentity (IMEI) number, Media Access Control address (MAC address), etc.

IIC 230 can include a transmitter component 232 and a receiver component234. Transmitter component 232 and receiver component 234 can facilitatesharing TFL information over a wireless interface. In an embodimenttransmitter component 232 and receiver component 234 can be an antennaand associated electronics for wireless communications, such as thoseenumerated elsewhere herein. In another embodiment, transmittercomponent 232 and receiver component 234 can facilitate determiningaspects of an employed wireless communications technology, such asdetermining a typical effective range for sharing TFL information over aBluetooth link. The determined effective range can then be employed indetermining a level of error associated with a location determinationbased on the shared TFL information.

FIG. 3 illustrates a system 300, which facilitates sharing TFLinformation in accordance with aspects of the subject disclosure. In oneembodiment, system 300 can be embodied in a UE that can share TFLinformation with other devices requesting sharing, e.g., a TFL sourcedevice. System 300 can include TFLIC component 310. TFLIC 310 canfacilitate access to TFL information. TFLIC 310 can be communicativelycoupled to TFL-AAC 320. AAC 320 can determine a level of TFL informationaccess based on a request for access to TFL information. AAC 320 can becommunicatively coupled to TFL-IIC. IIC 130 can facilitate interactionbetween a TFL source device and other devices.

IIC 330 can include a transmitter component 332 and a receiver component334. Transmitter component 332 and receiver component 334 can facilitatesharing TFL information over a wireless interface. In an embodimenttransmitter component 332 and receiver component 334 can be electronicsor software for wireless communications, such as those enumeratedelsewhere herein. In another embodiment, transmitter component 332 andreceiver component 334 can facilitate determining aspects of an employedwireless communications technology. In an aspect, transmitter component332 and receiver component 334 can be associated with receiving arequest to share TFL information and facilitating access to shared TFLinformation.

IIC 330 can be communicatively coupled to short-range antenna component336. Short-range antenna component 336 can facilitate communicatingbetween UEs to facilitate sharing TFL information. In some embodiments,short-range antenna component 336 can be associated with predeterminedtransmission regions. These transmission regions can be, for example,associated with a personal area network. A personal area network can belimited to devices on or near a user and can, for example, be associatedwith a range of about two meters. The exemplary short-range antennacomponent 336 coving about two meters would facilitate sharing TFLinformation from a TFL source device to other devices within about twometers of the TFL source device. This can be an efficient way of sharingTFL information among location enabled and non-location enabled devicesof a single person, such as sharing a location sourced from aTFL-enabled cell phone to a laptop, watch, PDA, running shoe fob, etc.,of a user to enable location-centric behavior on those devices. Otherranges can be employed and are within the scope of the presentdisclosure despite not being explicitly recited.

FIG. 4 is a depiction of a system 400, which facilitates receivingshared TFL information in in accordance with aspects of the subjectdisclosure. In one embodiment, system 400 can be embodied in a UE thatcan request TFL information from a TFL source device. System 400 caninclude short-range antenna component 450. Short-range antenna component450 can facilitate communication between various UEs to facilitatesharing TFL information. In some embodiments, short-range antennacomponent 450 can be associated with predetermined transmission regionsthat can include, for example, a personal area network. In anembodiment, short-range antenna component 450 can be the same as, orsimilar to, short-range antenna component 336 of system 300.

Short-range antenna component 450 can be communicatively coupled totransmitter component 452 and receiver component 454. Transmittercomponent 452 and receiver component 454 can facilitate sharing TFLinformation over a wireless interface. In an embodiment transmittercomponent 452 and receiver component 452 can be electronics or softwarefor wireless communications, such as those enumerated elsewhere herein.In another embodiment, transmitter component 452 and receiver component454 can facilitate determining aspects of an employed wirelesscommunications technology. In some embodiments, transmitter component452 and receiver component 454 can be the same as, or similar totransmitter component 332 and receiver component 334 of system 300. Inan aspect, transmitter component 452 and receiver component 454 can beassociated with facilitating access to a request to share TFLinformation and accessing shared TFL information.

Transmitter component 452 and receiver component 454 can becommunicatively coupled to TFL source device proximity component 460.TFL source device proximity component 460 can facilitate determining theproximity of a TFL source device to a component of system 400. In anembodiment, TFL source device proximity component 460 can determine theproximity of a TFL source device based on a communication technologyemployed in communications with a TFL source device. As an example, TFLsource device proximity component 460 can determine that a TFL sourcedevice is within about 10 meters of a component of system 400 whenBluetooth technology is associated with communications to the TFL sourcedevice.

TFL source device proximity component 460 can be communicatively coupledto memory component 470. Memory component 470 can be a data store.Memory component 470 can be employed to store data related to sharingTFL information. Memory component 470 can comprise TFL based locationregister 472 that can store a location derived from TFL information.Memory component 470 can further comprise TFL information register 474that can store TFL timing information that can be employed to determinea location.

FIG. 5 illustrates an exemplary system 500 including shared TFLinformation in accordance with aspects of the subject disclosure. System500 can include NodeBs 598A-D. Combinations of NodeBs 598A-D can act asNBSPs for determining TFL information. UE 580 can be a TFL-enabled UE.UE 580 can acquire TFL timing or location information relative to NodeBs598A-D. UE 580 can be associated with a short-range communication region581. UE 580 can be a TFL source device.

UEs 582 and 583 can be other UEs within the short-range communicationregion 581 of UE 580. Each of UE 582 can comprise a system that is thesame as, or similar to, system 400 as disclosed herein. As such, each ofUE 582 and UE 583 can generate a request to share TFL information. UE580 can comprise a system that can be the same as, or similar to, system300. As such, UE 580 can receive a request to share TFL information. UE580 can further determine a level of access authorization for TFLinformation and can facilitate access to TFL information in accordancewith the determined level of access authorization. UE 582 and UE 583 canreceive TFL information shared from UE 580.

In an embodiment, the range of short-range communication region 581 canbe determined. Based on this determination, locations determined on theshared TFL information at UE 582 and UE 583 can be associated with anerror. In other embodiments, based on this error, a correction factorcan be applied to the location determined from the shared TFLinformation where an error is associated with the determined location.

UE 583 can be associated with a short-range communication region 584. UE585 can be within short-range communication region 584. As such, UE 583can act as a TFL source device to share TFL information with UE 585. Inan embodiment, this type of iterative sharing of TFL information can belimited by access authorization determination factors. In otherembodiments, iterative-type sharing of TFL information can be identifiedwith additional levels of error in subsequent location determinationsbased on the associated iterative level of TFL sharing. In furtherembodiments, iterative-type TFL sharing can be prohibited. UE 586 can beoutside short-range communication region 581 and short-rangecommunication region 584. In some embodiments, UE 586 can be consideredoutside of range for sharing TFL information.

As an example, UE 580 can be a modern TFL-enabled cell phone. Each ofUEs 582, 583, 585 and 586 can be legacy cell phones that are not capableof directly determining their locations by way of conventionaltechnologies such as GPS, triangulation, multilateration, etc. As such,where it is desirable to enable location-centric functionality in UEs582, 583, 585 and 586, sharing TFL information with UE 580 can also bedesirable. As illustrated in exemplary system 600, UE 582 and 583 can bewithin range, e.g., short-range communication region 581, of 580 and canrequest and receive shared TFL information from TFL source device UE580. UE 585 can request a secondary share of TFL information from UE 580by way of UE 583 where UE 585 is within range of UE 583, e.g.,short-range communication region 584, and UE 583 is within range of UE580, e.g., short-range communication region 581. UE 586 can be beyond ashort-range communication region and can thus be unable to successfullycommunication a request to share TFL information with the other UEs ofsystem 600.

This example illustrates that TFL information can be shared amongdevices. This TFL information can be employed in location-centricfunctions on UEs 582, 583 and 585. Levels of error inherent in thelocations of UEs 582, 583 and 585 determined from the shared TFLinformation can be assessed, such as by estimating the area of shortrange communication region 581 and/or short range communication region584. Further, these determined errors can be compensated for. Of note,where short range communication region 581, and also short rangecommunication region 584, are relatively small in view of a bin-gridframework granularity associated with TFL information, the error canhave little to no effect on the determined location. As an example,where the bin grid array granularity is 10 meters, a short-rangecommunication region that has a radius of five meters would likely havean error that is less than the level of granularity and, as such, adetermined location would likely be within one bin grid of the locationof the TFL source device. Similarly, where the short-range communicationregion 581, for example, is about two meters, such as for a personalarea network, the determined error can be much less than the level ofgranularity and the shared TFL information can be presumed to allowcomputation of locations that do not need to be corrected. Thus, where auser's devices share TFL information to allow location-centricfunctionality for devices that request sharing of TFL information, theresulting location determinations can effectively be treated as correctlocations.

FIG. 5 is presented only to better illustrate some of the benefits ofthe presently disclosed subject matter and is explicitly not intended tolimit the scope of the disclosure to the various aspects particular tothe presently illustrated non-limiting example. In some embodiments, theuse of GPS or other location technology can be included as complimentaryto TFL information without departing from the scope of the presentdisclosure. It is noteworthy that GPS or other location information froma UE is not required to determine TFL information as disclosed in therelated application. Thus, even where legacy UEs, e.g., UEs without GPSor eGPS capabilities, are represented in system 500, the timinginformation from those legacy devices can be employed in TFL informationdeterminations. This can be particularly useful in regions that havelimited distribution of GPS enabled UEs or where GPS functions poorlydue to environmental factors such as urban cores, mountainous regions,etc.

In view of the example system(s) described above, example method(s) thatcan be implemented in accordance with the disclosed subject matter canbe better appreciated with reference to flowcharts in FIG. 6-FIG. 8. Forpurposes of simplicity of explanation, example methods disclosed hereinare presented and described as a series of acts; however, it is to beunderstood and appreciated that the claimed subject matter is notlimited by the order of acts, as some acts may occur in different ordersand/or concurrently with other acts from that shown and describedherein. For example, one or more example methods disclosed herein couldalternatively be represented as a series of interrelated states orevents, such as in a state diagram. Moreover, interaction diagram(s) mayrepresent methods in accordance with the disclosed subject matter whendisparate entities enact disparate portions of the methodologies.Furthermore, not all illustrated acts may be required to implement adescribed example method in accordance with the subject specification.Further yet, two or more of the disclosed example methods can beimplemented in combination with each other, to accomplish one or moreaspects herein described. It should be further appreciated that theexample methods disclosed throughout the subject specification arecapable of being stored on an article of manufacture (e.g., acomputer-readable medium) to allow transporting and transferring suchmethods to computers for execution, and thus implementation, by aprocessor or for storage in a memory.

FIG. 6 illustrates aspects of a method 600 facilitating sharing TFLinformation in accordance with aspects of the subject disclosure. At610, TFL information can be received. TFL information can be locationinformation derived from TFL timing information or TFL timinginformation that can facilitate determining a location. TFL informationcan include information to determine a differential value for a NodeBsite pair and a bin grid frame, as disclosed in more detail inincorporated U.S. Ser. No. 12/712,424.

TFL information can include location information or timing informationas disclosed in more detail in U.S. Ser. No. 12/712,424 filed Feb. 25,2010, which application is hereby incorporated by reference in itsentirety. Further, such information can be received from active state oridle state user equipment as disclosed in more detail in U.S. Ser. No.12/836,471, filed Jul. 14, 2010, which application is also herebyincorporated by reference in its entirety. As such, TFL information caninclude location information for a UE, in an active or idle state, basedon timing information. As a non-limiting example, a mobile device,including mobile devices not equipped with a GPS-type system, can belocated by looking up timing information associated with the mobiledevice from a TFL information reference. As such, the exemplary mobiledevice can be located using TFL information without employing GPS-typetechniques. In an aspect, TFL information can include information todetermine a DV(?,X). The centroid region (possible locations between anysite pair) for an observed time value associated with any NodeB sitepair (NBSP) can be calculated and is related to the determined value (inunits of chip) from any pair of NodeBs. When UE time data is accessed, aDV(?,X) look-up can be initiated. Relevant NBSPs can be prioritized aspart of the look-up. Further, the relevant pairs can be employed as anindex to lookup a first primary set. As an example, time data for a UEcan be accessed in relation to a locating event in a TFL wirelesscarrier environment. In this example, it can be determined that a NBSP,with a first reference frame, be used for primary set lookup with thecomputed DV(?,X) value as the index. This can for example return a setof bin grid frames locations forming a hyperbola between the NodeBs ofthe NBSP. A second lookup can then be performed for an additionalrelevant NBSP, with a second reference frame, using the same valueDV(?,X), as an index into the data set. Continuing the example, thereturned set for the look up with second NBSP can return a second set ofbin grid frames. Thus, the UE is likely located in both sets of bin gridframes. Therefore, where the UE is most likely in both sets, it isprobable that the location for the UE is at the intersection of the twosets. Additional NBSPs can be included to further narrow the possiblelocations of the UE. Employing TFL information for locationdetermination is demonstrably different from conventional locationdetermination techniques or systems such as GPS, eGPS, triangulation ormultilateration in wireless carrier environments, near field techniques,or proximity sensors.

At 620, a request for access to the TFL information can be received. Inan embodiment, the request can be generated at devices seeking TFLinformation from TFL source devices. Receiving the request can includereceiving information relating to the requesting system. Examples ofinformation relating to the requesting system can include deviceidentifiers, user identifiers or names, wireless carrier providerinformation, range information, communications technology information,intended use of shared TFL information, etc. In some embodiments,receiving a request for access to the TFL information at 620 can bebased on user actions, such as “bumping”. In other embodiments,receiving the request can be automatically processed or processed basedon a predetermined set of criteria being satisfied.

At 630, a level of access authorization can be determined. Determiningthe level of access authorization can be based on the request forinformation received at 620. In an aspect, this can include basing thedetermination on information relating to the requesting system. As anexample, a level of access authorization can be determined based on useridentification for a UE requesting access to shared TFL information froma TFL source device. Determinations can include satisfying a sharingrule, not satisfying a sharing rule, satisfying part of a sharing rule,applying a sharing rule to a set of information, etc. A determinationrelating to a sharing rule can be related to TFL information or a levelof access to TFL information. At 640, a level of access to the TFLinformation can be allowed based on the determine level of accessauthorization from 630. At this point, method 600 can end.

FIG. 7 illustrates aspects of a method 700 requesting sharing of TFLinformation in accordance with aspects of the subject disclosure. At710, information related to a TFL source device can be received. A TFLsource device can be a UE that can share TFL information. In anembodiment, a TFL source device can make available informationidentifying it as a TFL source device. In other embodiments, additionalinformation can be included in the information made available andidentifying a device as a TFL source device. This information can bereceived, for example, in a different device employing system 700. Thisinformation can be employed in making a determination to request sharingof TFL information with the TFL source device. As an example, where afirst TFL source device identifies as belonging to Mozart, a seconddevice, also belonging to Mozart, can determine that a request forsharing TFL information is appropriate because the TFL source devicebelongs to the same person, namely Mozart. Alternatively, where thesecond device belongs to Beethoven, a determination that a requestshould not be generated can be made because, for example, the twodevices belong to different people.

At 720, a proximity to the TFL source device can be determined. Theproximity can be employed in determining an amount of error that can beinherent in shared TFL information. Where a level of error crosses athreshold level, a determination can be made not to generate a requestfor sharing TFL information because the value of any shared TFLinformation in determining a location of a device requesting the sharedTFL information in below an acceptable level due to the inherent error.As an example, where a range is greater than 100 meters, and an errormay therefore greatly exceed a location with a bin grid array pitch of20 meters, it can be determined that sharing TFL information is notsufficiently accurate enough to justify the sharing of the TFLinformation. However, where a proximity is close, such as for a personalarea network, the error is likely to be small and a request for TFLinformation can be desirable.

At 730, a request for access to TFL information of the TFL source devicecan be generated. The request can include information about therequesting device. This information can include device identifiers, useridentifiers or names, wireless carrier provider information, rangeinformation, communications technology information, intended use ofshared TFL information, etc. In an embodiment, a TFL source devicereceiving a request, such as that generated at 730, can process therequest to determine a level of access authorization. Based on thislevel, access to the TFL information of the TFL source device can becorrespondingly adapted. At 740, TFL information of the TFL sourcedevice can be received. At this point, method 700 can end.

FIG. 8 illustrates a method 800 that facilitates receiving shared TFLinformation in accordance with aspects of the subject disclosure. At810, a request at a first device for access to TFL information of a TFLsource can be generated. The request can include information about therequesting device. This information can include device identifiers, useridentifiers or names, wireless carrier provider information, rangeinformation, communications technology information, intended use ofshared TFL information, etc. At 820, a proximity to the TFL sourcedevice can be determined. The proximity can be employed in determiningan amount of error that can be inherent in shared TFL information. At830, TFL information of the TFL source device can be received at thefirst device.

At 840, a probable location of the first device can be determined basedon the TFL information of the TFL source device. In an embodiment, TFLcalculations can be made on the shared TFL information. Whereas the TFLinformation can be shared between the TFL source device and the firstdevice, the locations can also be determined to be the same. In anaspect, it can be similar to two people sitting on a bus and the firstperson asks the second, “Where are we?” The second person replies, “At42^(nd) and Park Ave.” The first person can then accept that they tooare at 42^(nd) and Park Ave.

At 850, a level of error can be associated with the location based onthe determined proximity between the first device and the TFL sourcedevice. At this point, method 800 can end. Where the two devices arefurther apart, the error in location can increase as disclosedhereinabove. As such, even where the first device determines that thelocation is the same as the location of the TFL sharing device, an errorcan be determined and compensated for. Continuing the above example,even though the first person accepts that they too are on 42^(nd) andPark Ave., where they are at the front of the bus and the second personis at the back of the bus, an error of the length of the bus can bepresumed. Thus, the first person is the length of the bus ahead of thesecond person. This is a trivial error when the granularity of thelocations is on the order of city blocks and therefor no correction maybe made in any computations made by the first person. In a differentexample, the level of error can be more critical and can be compensatedfor.

Method 800 can allow devices to receive and employ shared TFLinformation. In an aspect, this can allow the location of a TFL enableddevice to be employed by non-TFL enabled devices for location-centricservices. Where location-centric behavior is becoming more commonplacefor mobile devices, it can still be difficult to employ on non-mobiledevices, such as desktop computers that generally rely on determininglocation by tracing an internet protocol address. A TFL-enabled cellphone can quickly share TFL information with a desktop computer to allowthe desktop to determine that it is located at the same location, withan inherent level of error, as the TFL-enabled cell phone. Thisdetermination can allow the desktop computer to perform location-centricfunctions with location information approaching the accuracy of thesharing TFL-enabled cell phone.

FIG. 9 presents an example embodiment 900 of a mobile network platform910 that can implement and exploit one or more aspects of the subjectmatter described herein. Generally, wireless network platform 910 caninclude components, e.g., nodes, gateways, interfaces, servers, ordisparate platforms, that facilitate both packet-switched (PS) (e.g.,internet protocol (IP), frame relay, asynchronous transfer mode (ATM))and circuit-switched (CS) traffic (e.g., voice and data), as well ascontrol generation for networked wireless telecommunication. As anon-limiting example, wireless network platform 910 can be included aspart of a telecommunications carrier network. Mobile network platform910 includes CS gateway node(s) 912 which can interface CS trafficreceived from legacy networks like telephony network(s) 940 (e.g.,public switched telephone network (PSTN), or public land mobile network(PLMN)) or a signaling system #7 (SS7) network 970. Circuit switchedgateway node(s) 912 can authorize and authenticate traffic (e.g., voice)arising from such networks. Additionally, CS gateway node(s) 912 canaccess mobility, or roaming, data generated through SS7 network 970; forinstance, mobility data stored in a visited location register (VLR),which can reside in memory 930. Further, TFL information can be storedin memory 930. In an aspect, the TFL information can be based on timingsignals associated with communication between mobile network platform910 and mobile device 975 by way of RAN 970. Moreover, CS gatewaynode(s) 912 interfaces CS-based traffic and signaling and PS gatewaynode(s) 918. As an example, in a 3GPP UMTS network, CS gateway node(s)912 can be realized at least in part in gateway GPRS support node(s)(GGSN). It should be appreciated that functionality and specificoperation of CS gateway node(s) 912, PS gateway node(s) 918, and servingnode(s) 916, can be provided and dictated by radio technology(ies)utilized by mobile network platform 910 for telecommunication.

In addition to receiving and processing CS-switched traffic andsignaling, PS gateway node(s) 918 can authorize and authenticatePS-based data sessions with served mobile devices. Data sessions caninclude traffic, or content(s), exchanged with networks external to thewireless network platform 910, like wide area network(s) (WANs) 950,enterprise network(s) 970, and service network(s) 980, which can beembodied in local area network(s) (LANs), can also be interfaced withmobile network platform 910 through PS gateway node(s) 918. It is to benoted that WANs 950 and enterprise network(s) 960 can embody, at leastin part, a service network(s) like IP multimedia subsystem (IMS). Basedon radio technology layer(s) available in technology resource(s) 917,packet-switched gateway node(s) 918 can generate packet data protocolcontexts when a data session is established; other data structures thatfacilitate routing of packetized data also can be generated. To thatend, in an aspect, PS gateway node(s) 918 can include a tunnel interface(e.g., tunnel termination gateway (TTG) in 3GPP UMTS network(s) (notshown)) which can facilitate packetized communication with disparatewireless network(s), such as Wi-Fi networks.

In embodiment 900, wireless network platform 910 also includes servingnode(s) 916 that, based upon available radio technology layer(s) withintechnology resource(s) 917, convey the various packetized flows of datastreams received through PS gateway node(s) 918. It is to be noted thatfor technology resource(s) 917 that rely primarily on CS communication,server node(s) can deliver traffic without reliance on PS gatewaynode(s) 918; for example, server node(s) can embody at least in part amobile switching center. As an example, in a 3GPP UMTS network, servingnode(s) 916 can be embodied in serving GPRS support node(s) (SGSN).

For radio technologies that exploit packetized communication, server(s)914 in wireless network platform 910 can execute numerous applicationsthat can generate multiple disparate packetized data streams or flows,and manage (e.g., schedule, queue, format . . . ) such flows. Suchapplication(s) can include add-on features to standard services (forexample, provisioning, billing, customer support . . . ) provided bywireless network platform 910. Data streams (e.g., content(s) that arepart of a voice call or data session) can be conveyed to PS gatewaynode(s) 918 for authorization/authentication and initiation of a datasession, and to serving node(s) 916 for communication thereafter. Inaddition to application server, server(s) 914 can include utilityserver(s), a utility server can include a provisioning server, anoperations and maintenance server, a security server that can implementat least in part a certificate authority and firewalls as well as othersecurity mechanisms, and the like. In an aspect, security server(s)secure communication served through wireless network platform 910 toensure network's operation and data integrity in addition toauthorization and authentication procedures that CS gateway node(s) 912and PS gateway node(s) 918 can enact. Moreover, provisioning server(s)can provision services from external network(s) like networks operatedby a disparate service provider; for instance, WAN 950 or GlobalPositioning System (GPS) network(s) (not shown). Provisioning server(s)can also provision coverage through networks associated to wirelessnetwork platform 910 (e.g., deployed and operated by the same serviceprovider), such as femto-cell network(s) (not shown) that enhancewireless service coverage within indoor confined spaces and offload RANresources in order to enhance subscriber service experience within ahome or business environment.

It is to be noted that server(s) 914 can include one or more processorsconfigured to confer at least in part the functionality of macro networkplatform 910. To that end, the one or more processor can execute codeinstructions stored in memory 930, for example. It should be appreciatedthat server(s) 914 can include a content manager 915, which operates insubstantially the same manner as described hereinbefore.

In example embodiment 900, memory 930 can store information related tooperation of wireless network platform 910. Other operationalinformation can include provisioning information of mobile devicesserved through wireless platform network 910, subscriber databases;application intelligence, pricing schemes, e.g., promotional rates,flat-rate programs, couponing campaigns; technical specification(s)consistent with telecommunication protocols for operation of disparateradio, or wireless, technology layers; and so forth. Memory 930 can alsostore information from at least one of telephony network(s) 940, WAN950, enterprise network(s) 960, or SS7 network 970. In an aspect, memory930 can be, for example, accessed as part of a data store component oras a remotely connected memory store.

In order to provide a context for the various aspects of the disclosedsubject matter, FIG. 10, and the following discussion, are intended toprovide a brief, general description of a suitable environment in whichthe various aspects of the disclosed subject matter can be implemented.While the subject matter has been described above in the general contextof computer-executable instructions of a computer program that runs on acomputer and/or computers, those skilled in the art will recognize thatthe disclosed subject matter also can be implemented in combination withother program modules. Generally, program modules include routines,programs, components, data structures, etc. that perform particulartasks and/or implement particular abstract data types.

In the subject specification, terms such as “store,” “storage,” “datastore,” data storage,” “database,” and substantially any otherinformation storage component relevant to operation and functionality ofa component, refer to “memory components,” or entities embodied in a“memory” or components comprising the memory. It will be appreciatedthat the memory components described herein can be either volatilememory or nonvolatile memory, or can include both volatile andnonvolatile memory.

By way of illustration, and not limitation, nonvolatile memory, forexample, can be included in volatile memory 1020, non-volatile memory1022 (see below), disk storage 1024 (see below), and memory storage 1046(see below). Further, nonvolatile memory can be included in read onlymemory (ROM), programmable ROM (PROM), electrically programmable ROM(EPROM), electrically erasable ROM (EEPROM), or flash memory. Volatilememory can include random access memory (RAM), which acts as externalcache memory. By way of illustration and not limitation, RAM isavailable in many forms such as synchronous RAM (SRAM), dynamic RAM(DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM),enhanced SDRAM (ESDRAM), Synchlink DRAM (SLDRAM), and direct Rambus RAM(DRRAM). Additionally, the disclosed memory components of systems ormethods herein are intended to comprise, without being limited tocomprising, these and any other suitable types of memory.

Moreover, it will be noted that the disclosed subject matter can bepracticed with other computer system configurations, includingsingle-processor or multiprocessor computer systems, mini-computingdevices, mainframe computers, as well as personal computers, hand-heldcomputing devices (e.g., PDA, phone, watch, tablet computers, . . . ),microprocessor-based or programmable consumer or industrial electronics,and the like. The illustrated aspects can also be practiced indistributed computing environments where tasks are performed by remoteprocessing devices that are linked through a communications network;however, some if not all aspects of the subject disclosure can bepracticed on stand-alone computers. In a distributed computingenvironment, program modules can be located in both local and remotememory storage devices.

FIG. 10 illustrates a block diagram of a computing system 1000 operableto execute the disclosed systems and methods in accordance with anembodiment. Computer 1012 includes a processing unit 1014, a systemmemory 1016, and a system bus 1018. In an embodiment, computer 1012 canbe part of the hardware of a timed fingerprint location component.System bus 1018 couples system components including, but not limited to,system memory 1016 to processing unit 1014. Processing unit 1014 can beany of various available processors. Dual microprocessors and othermultiprocessor architectures also can be employed as processing unit1014.

System bus 1018 can be any of several types of bus structure(s)including a memory bus or a memory controller, a peripheral bus or anexternal bus, and/or a local bus using any variety of available busarchitectures including, but not limited to, Industrial StandardArchitecture (ISA), Micro-Channel Architecture (MS A), Extended ISA(EISA), Intelligent Drive Electronics, VESA Local Bus (VLB), PeripheralComponent Interconnect (PCI), Card Bus, Universal Serial Bus (USB),Advanced Graphics Port (AGP), Personal Computer Memory CardInternational Association bus (PCMCIA), Firewire (IEEE 1194), and SmallComputer Systems Interface (SCSI).

System memory 1016 includes volatile memory 1020 and nonvolatile memory1022. A basic input/output system (BIOS), containing routines totransfer information between elements within computer 1012, such asduring start-up, can be stored in nonvolatile memory 1022. By way ofillustration, and not limitation, nonvolatile memory 1022 can includeROM, PROM, EPROM, EEPROM, or flash memory. Volatile memory 1020 includesRAM, which acts as external cache memory. By way of illustration and notlimitation, RAM is available in many forms such as SRAM, dynamic RAM(DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM),enhanced SDRAM (ESDRAM), Synchlink DRAM (SLDRAM), Rambus direct RAM(RDRAM), direct Rambus dynamic RAM (DRDRAM), and Rambus dynamic RAM(RDRAM).

Computer 1012 also includes removable/non-removable,volatile/non-volatile computer storage media. FIG. 10 illustrates, forexample, disk storage 1024. Disk storage 1024 includes, but is notlimited to, devices like a magnetic disk drive, floppy disk drive, tapedrive, flash memory card, or memory stick. In addition, disk storage1024 can include storage media separately or in combination with otherstorage media including, but not limited to, an optical disk drive suchas a compact disk ROM device (CD-ROM), CD recordable drive (CD-R Drive),CD rewritable drive (CD-RW Drive) or a digital versatile disk ROM drive(DVD-ROM). To facilitate connection of the disk storage devices 1024 tosystem bus 1018, a removable or non-removable interface can be used,such as interface 1026. In an embodiment, disk storage 1024 can storeTFL lookup tables to facilitate lookup of location information based onNodeB site pairs and time values. In another embodiment, disk storage1024 can store TFL location information.

Computing devices can include a variety of media, which can includecomputer-readable storage media or communications media, which two termsare used herein differently from one another as follows.

Computer-readable storage media can be any available storage media thatcan be accessed by the computer and includes both volatile andnonvolatile media, removable and non-removable media. By way of example,and not limitation, computer-readable storage media can be implementedin connection with any method or technology for storage of informationsuch as computer-readable instructions, program modules, structureddata, or unstructured data. Computer-readable storage media can include,but are not limited to, RAM, ROM, EEPROM, flash memory or other memorytechnology, CD-ROM, digital versatile disk (DVD) or other optical diskstorage, magnetic cassettes, magnetic tape, magnetic disk storage orother magnetic storage devices, or other tangible and/or non-transitorymedia which can be used to store desired information. Computer-readablestorage media can be accessed by one or more local or remote computingdevices, e.g., via access requests, queries or other data retrievalprotocols, for a variety of operations with respect to the informationstored by the medium.

Communications media can embody computer-readable instructions, datastructures, program modules, or other structured or unstructured data ina data signal such as a modulated data signal, e.g., a carrier wave orother transport mechanism, and includes any information delivery ortransport media. The term “modulated data signal” or signals refers to asignal that has one or more of its characteristics set or changed insuch a manner as to encode information in one or more signals. By way ofexample, and not limitation, communication media include wired media,such as a wired network or direct-wired connection, and wireless mediasuch as acoustic, RF, infrared and other wireless media.

It can be noted that FIG. 10 describes software that acts as anintermediary between users and computer resources described in suitableoperating environment 1000. Such software includes an operating system1028. Operating system 1028, which can be stored on disk storage 1024,acts to control and allocate resources of computer system 1012. Systemapplications 1030 take advantage of the management of resources byoperating system 1028 through program modules 1032 and program data 1034stored either in system memory 1016 or on disk storage 1024. It is to benoted that the disclosed subject matter can be implemented with variousoperating systems or combinations of operating systems.

A user can enter commands or information into computer 1012 throughinput device(s) 1036. Input devices 1036 include, but are not limitedto, a pointing device such as a mouse, trackball, stylus, touch pad,keyboard, microphone, joystick, game pad, satellite dish, scanner, TVtuner card, digital camera, digital video camera, web camera, cellphone, smartphone, tablet computer, etc. These and other input devicesconnect to processing unit 1014 through system bus 1018 by way ofinterface port(s) 1038. Interface port(s) 1038 include, for example, aserial port, a parallel port, a game port, a universal serial bus (USB),an infrared port, a Bluetooth port, an IP port, or a logical portassociated with a wireless service, etc. Output device(s) 1040 use someof the same type of ports as input device(s) 1036.

Thus, for example, a USB port can be used to provide input to computer1012 and to output information from computer 1012 to an output device1040. Output adapter 1042 is provided to illustrate that there are someoutput devices 1040 like monitors, speakers, and printers, among otheroutput devices 1040, which use special adapters. Output adapters 1042include, by way of illustration and not limitation, video and soundcards that provide means of connection between output device 1040 andsystem bus 1018. It should be noted that other devices and/or systems ofdevices provide both input and output capabilities such as remotecomputer(s) 1044.

Computer 1012 can operate in a networked environment using logicalconnections to one or more remote computers, such as remote computer(s)1044. Remote computer(s) 1044 can be a personal computer, a server, arouter, a network PC, a workstation, a microprocessor based appliance, apeer device, or other common network node and the like, and can includemany or all of the elements described relative to computer 1012.

For purposes of brevity, only a memory storage device 1046 isillustrated with remote computer(s) 1044. Remote computer(s) 1044 can belogically connected to computer 1012 through a network interface 1048and then physically connected by way of communication connection 1050.Network interface 1048 encompasses wire and/or wireless communicationnetworks such as local-area networks (LAN) and wide-area networks (WAN).LAN technologies include Fiber Distributed Data Interface (FDDI), CopperDistributed Data Interface (CDDI), Ethernet, Token Ring and the like.WAN technologies include, but are not limited to, point-to-point links,circuit switching networks like Integrated Services Digital Networks(ISDN) and variations thereon, packet switching networks, and DigitalSubscriber Lines (DSL). As noted below, wireless technologies may beused in addition to or in place of the foregoing.

Communication connection(s) 1050 refer(s) to hardware/software employedto connect network interface 1048 to bus 1018. While communicationconnection 1050 is shown for illustrative clarity inside computer 1012,it can also be external to computer 1012. The hardware/software forconnection to network interface 1048 can include, for example, internaland external technologies such as modems, including regular telephonegrade modems, cable modems and DSL modems, ISDN adapters, and Ethernetcards.

The above description of illustrated embodiments of the subjectdisclosure, including what is described in the Abstract, is not intendedto be exhaustive or to limit the disclosed embodiments to the preciseforms disclosed. While specific embodiments and examples are describedherein for illustrative purposes, various modifications are possiblethat are considered within the scope of such embodiments and examples,as those skilled in the relevant art can recognize.

In this regard, while the disclosed subject matter has been described inconnection with various embodiments and corresponding figures, whereapplicable, it is to be understood that other similar embodiments can beused or modifications and additions can be made to the describedembodiments for performing the same, similar, alternative, or substitutefunction of the disclosed subject matter without deviating therefrom.Therefore, the disclosed subject matter should not be limited to anysingle embodiment described herein, but rather should be construed inbreadth and scope in accordance with the appended claims below.

As it employed in the subject specification, the term “processor” canrefer to substantially any computing processing unit or devicecomprising, but not limited to comprising, single-core processors;single-processors with software multithread execution capability;multi-core processors; multi-core processors with software multithreadexecution capability; multi-core processors with hardware multithreadtechnology; parallel platforms; and parallel platforms with distributedshared memory. Additionally, a processor can refer to an integratedcircuit, an application specific integrated circuit (ASIC), a digitalsignal processor (DSP), a field programmable gate array (FPGA), aprogrammable logic controller (PLC), a complex programmable logic device(CPLD), a discrete gate or transistor logic, discrete hardwarecomponents, or any combination thereof designed to perform the functionsdescribed herein. Processors can exploit nano-scale architectures suchas, but not limited to, molecular and quantum-dot based transistors,switches, and gates, in order to optimize space usage or enhanceperformance of user equipment. A processor may also be implemented as acombination of computing processing units.

As used in this application, the terms “component,” “system,”“platform,” “layer,” “selector,” “interface,” and the like are intendedto refer to a computer-related entity or an entity related to anoperational apparatus with one or more specific functionalities, whereinthe entity can be either hardware, a combination of hardware andsoftware, software, or software in execution. As an example, a componentmay be, but is not limited to being, a process running on a processor, aprocessor, an object, an executable, a thread of execution, a program,and/or a computer. By way of illustration and not limitation, both anapplication running on a server and the server can be a component. Oneor more components may reside within a process and/or thread ofexecution and a component may be localized on one computer and/ordistributed between two or more computers. In addition, these componentscan execute from various computer readable media having various datastructures stored thereon. The components may communicate via localand/or remote processes such as in accordance with a signal having oneor more data packets (e.g., data from one component interacting withanother component in a local system, distributed system, and/or across anetwork such as the Internet with other systems via the signal). Asanother example, a component can be an apparatus with specificfunctionality provided by mechanical parts operated by electric orelectronic circuitry, which can be operated by a software or firmwareapplication executed by a processor, wherein the processor can beinternal or external to the apparatus and executes at least a part ofthe software or firmware application. As yet another example, acomponent can be an apparatus that provides specific functionalitythrough electronic components without mechanical parts, the electroniccomponents can include a processor therein to execute software orfirmware that confers at least in part the functionality of theelectronic components.

In addition, the term “or” is intended to mean an inclusive “or” ratherthan an exclusive “or.” That is, unless specified otherwise, or clearfrom context, “X employs A or B” is intended to mean any of the naturalinclusive permutations. That is, if X employs A; X employs B; or Xemploys both A and B, then “X employs A or B” is satisfied under any ofthe foregoing instances. Moreover, articles “a” and “an” as used in thesubject specification and annexed drawings should generally be construedto mean “one or more” unless specified otherwise or clear from contextto be directed to a singular form.

Moreover, terms like “user equipment (UE),” “mobile station,” “mobile,”subscriber station,” “subscriber equipment,” “access terminal,”“terminal,” “handset,” and similar terminology, refer to a wirelessdevice utilized by a subscriber or user of a wireless communicationservice to receive or convey data, control, voice, video, sound, gaming,or substantially any data-stream or signaling-stream. The foregoingterms are utilized interchangeably in the subject specification andrelated drawings. Likewise, the terms “access point (AP),” “basestation,” “Node B,” “evolved Node B (eNode B),” “home Node B (HNB),”“home access point (HAP),” and the like, are utilized interchangeably inthe subject application, and refer to a wireless network component orappliance that serves and receives data, control, voice, video, sound,gaming, or substantially any data-stream or signaling-stream to and froma set of subscriber stations or provider enabled devices. Data andsignaling streams can include packetized or frame-based flows.

Additionally, the term “core-network”, “core”, “core carrier network”,or similar terms can refer to components of a telecommunications networkthat provide some or all of aggregation, authentication, call controland switching, charging, service invocation, or gateways. Aggregationcan refer to the highest level of aggregation in a service providernetwork wherein the next level in the hierarchy under the core nodes canbe the distribution networks and then the edge networks. UEs do notnormally connect directly to the core networks of a large serviceprovider but can be routed to the core by way of a switch or radio areanetwork. Authentication can refer to determinations regarding whetherthe user requesting a service from the telecom network is authorized todo so within this network or not. Call control and switching can referdeterminations related to the future course of a call stream acrosscarrier equipment based on the call signal processing. Charging can berelated to the collation and processing of charging data generated byvarious network nodes. Two common types of charging mechanisms found inpresent day networks can be prepaid charging and postpaid charging.Service invocation can occur based on some explicit action (e.g. calltransfer) or implicitly (e.g., call waiting). It is to be noted thatservice “execution” may or may not be a core network functionality asthird party network/nodes may take part in actual service execution. Agateway can be present in the core network to access other networks.Gateway functionality can be dependent on the type of the interface withanother network.

Furthermore, the terms “user,” “subscriber,” “customer,” “consumer,”“prosumer,” “agent,” and the like are employed interchangeablythroughout the subject specification, unless context warrants particulardistinction(s) among the terms. It should be appreciated that such termscan refer to human entities or automated components (e.g., supportedthrough artificial intelligence, as through a capacity to makeinferences based on complex mathematical formalisms), that can providesimulated vision, sound recognition and so forth.

Aspects, features, or advantages of the subject matter can be exploitedin substantially any, or any, wired, broadcast, wirelesstelecommunication, radio technology or network, or combinations thereof.Non-limiting examples of such technologies or networks include Geocasttechnology; broadcast technologies (e.g., sub-Hz, ELF, VLF, LF, MF, HF,VHF, UHF, SHF, THz broadcasts, etc.); Ethernet; X.25; powerline-typenetworking (e.g., PowerLine AV Ethernet, etc.); femto-cell technology;Wi-Fi; Zigbee, other 802.XX wireless technologies, WorldwideInteroperability for Microwave Access (WiMAX); Enhanced General PacketRadio Service (Enhanced GPRS); Third Generation Partnership Project(3GPP or 3G) Long Term Evolution (LTE); 3GPP Universal MobileTelecommunications System (UMTS) or 3GPP UMTS; Third GenerationPartnership Project 2 (3GPP2) Ultra Mobile Broadband (UMB); High SpeedPacket Access (HSPA); High Speed Downlink Packet Access (HSDPA); HighSpeed Uplink Packet Access (HSUPA); GSM Enhanced Data Rates for GSMEvolution (EDGE) Radio Access Network (RAN) or GERAN; UMTS TerrestrialRadio Access Network (UTRAN); or LTE Advanced.

What has been described above includes examples of systems and methodsillustrative of the disclosed subject matter. It is, of course, notpossible to describe every combination of components or methodologieshere. One of ordinary skill in the art may recognize that many furthercombinations and permutations of the claimed subject matter arepossible. Furthermore, to the extent that the terms “includes,” “has,”“possesses,” and the like are used in the detailed description, claims,appendices and drawings such terms are intended to be inclusive in amanner similar to the term “comprising” as “comprising” is interpretedwhen employed as a transitional word in a claim.

What is claimed is:
 1. A system, comprising: a processor; and a memorythat stores executable instructions that, when executed by theprocessor, facilitate performance of operations, comprising: receivingan indication that timed fingerprint location information associatedwith a first device has been received at a second device, wherein thetimed fingerprint location information comprises a first differentialtime value for a NodeB site pair comprising a first NodeB device and asecond NodeB device and a second differential time value for anotherNodeB site pair comprising a third NodeB device, wherein the first andsecond differential time values are correlated to geographic locationinformation determined before the timed fingerprint location informationis received, and wherein the first and second differential time valuesare stored as part of the timed fingerprint location information toenable determining a first location corresponding to the first andsecond differential time values; receiving, via an informationinterface, a sharing value related to another indication of a permissionrelated to shared access to the timed fingerprint location informationbetween devices; and enabling access by the second device to the firstand second differential time values of the timed fingerprint locationinformation associated with the first device based on the sharing value,to enable determination of a second location of the second device basedon information received from a timed fingerprint location informationdata store and the timed fingerprint location information associatedwith the first device.
 2. The system of claim 1, wherein the seconddifferential time value is related to the other NodeB site paircomprising the third NodeB device and a fourth NodeB device.
 3. Thesystem of claim 1, wherein the timed fingerprint location informationassociated with the first device is accessible by a third device, basedon the sharing value, to enable determining a third location of thethird device.
 4. The system of claim 1, wherein a permissiondetermination is based on the sharing value and requestor informationassociated with a request to share the timed fingerprint locationinformation.
 5. The system of claim 4, wherein the requestor informationcomprises an identity of a user of the second device.
 6. The system ofclaim 4, wherein the requestor information comprises an identity of thesecond device.
 7. The system of claim 1, further comprising: receivinghistoric timed fingerprint location information that comprises ahistoric differential time value to facilitate a corresponding historiclocation determination stored by a timed fingerprint location data storebased on the historic ‘differential time value.
 8. The system of claim1, wherein the operations further comprise determining an indicatorrelating to satisfaction of a condition relating to the shared access tothe timed fingerprint location information has been received from thefirst device.
 9. The system of claim 8, wherein the condition isupdateable.
 10. A method, comprising: receiving, by a first userequipment comprising a processor, timed fingerprint location informationfor a second user equipment, wherein the timed fingerprint locationinformation comprises a first differential time value for a NodeB sitepair comprising a first NodeB device and a second NodeB device and asecond differential time value for another NodeB site pair comprising athird NodeB device, wherein the first and second differential timevalues are correlated to geographic location information determinedbefore the timed fingerprint location information is received by thefirst user equipment, and wherein the first and second differential timevalues are stored as part of the timed fingerprint location informationto facilitate determining a first location corresponding to the firstand second differential time values; receiving, via an informationinterface of the first user equipment, a permission value related toallowing shared access to the timed fingerprint location informationbetween the first user equipment and the second user equipment; andallowing the first user equipment to access a portion of the timedfingerprint location information, based on the permission value, toenable determining a second location for the first user equipment basedon the timed fingerprint location information for the second userequipment.
 11. The method of claim 10, further comprising, determining,by the first user equipment, an access value based on the permissionvalue and information related to the second user equipment.
 12. Themethod of claim 11, wherein the determining the access value comprisesidentifying a user identity associated with the second user equipment.13. The method of claim 11, wherein the determining the access valuecomprises identifying the second user equipment.
 14. The method of claim10, wherein the allowing the first user equipment to access to theportion of the timed fingerprint location information comprising thefirst and second differential time values is based on a privacy policyassociated with the first user equipment.
 15. A mobile device,comprising: a processor; and a memory that stores executableinstructions that, when executed by the processor, facilitateperformance of operations, comprising: receiving timed fingerprintlocation information related to another mobile device, the timedfingerprint location information comprising a first differential timevalue for a NodeB site pair comprising a first NodeB device and a secondNodeB device and a second differential time value for another NodeB sitepair comprising a third NodeB device, wherein the first and seconddifferential time values are correlated to geographic locationinformation determined before the timed fingerprint location informationis received, and wherein the first and second differential time valuesare stored as part of the timed fingerprint location information tofacilitate determining a first location corresponding to the first andsecond differential time values; receiving, via an graphical userinterface of the mobile device, a permission indicator related to apermission for sharing access to the timed fingerprint locationinformation of the other mobile device; and sharing the timedfingerprint location information with the mobile device based on thepermission indicator, enabling determination of a second location forthe mobile device based on the timed fingerprint location informationrelated to the other mobile device.
 16. The mobile device of claim 15,wherein the permission is based on receiving, by the mobile device, anidentity of a user associated with the other mobile device.
 17. Themobile device of claim 15, wherein the permission is based on receiving,by the mobile device, an identity of the other mobile device.
 18. Themobile device of claim 15, wherein the permission is based on receiving,by the mobile device, a privacy value stored at the mobile device. 19.The mobile device of claim 15, wherein the permission is based onreceiving, by the mobile device, a privacy value from the other mobiledevice.
 20. The mobile device of claim 15, wherein the receiving thetimed fingerprint location information comprising the first and seconddifferential time values comprises receiving a historical differentialtime value.